Making changes to formal specifications: requirements and an example
نویسندگان
چکیده
منابع مشابه
Adding Formal Specifications to Requirements Patterns∗
Embedded systems usually must achieve a higher level of robustness and reliability because they control real-world physical processes or devices upon which we depend, frequently, in a critical way. Consequently, methods for modeling and developing embedded systems and rigorously verifying behavior before committing to code are increasingly important. In order to use object-oriented development ...
متن کاملAn Authoring Tool for Informal and Formal Requirements Specifications
We describe foundations and design principles of a tool that supports authoring of informal and formal software requirements specifications simultaneously and from a single source. The tool is an attempt to bridge the gap between completely informal requirements specifications (as found in practice) and formal ones (as needed in formal methods). The user is supported by an interactive syntax-di...
متن کاملThe Validation of Formal Specifications of Requirements
We review the approaches put forward to validate formal specifications of requirements, drawing a parallel with research into the validation of knowledge bases. Using an industrial-scale case study we describe a partially implemented, integrated environment for validating requirements stated in many-sorted first order logic. In particular, we show how techniques from machine learning can be use...
متن کاملAn introduction to Z and formal specifications
This article is an introduction to the description of information systems using formal, mathematical specifications written in the Z notation, and to the refinement of these specifications into rigorously-checked designs. The first part introduces the idea of a formal specification using a simple example: that of a “birthday book” in which people’s birthdays can be recorded, and which is able t...
متن کاملFrom Requirements Models to Formal Specifications in B
The development of critical systems requires a high assurance process from requirements to the running code. Formal methods, such as B, now provide industry-strength tools to develop abstract models, refine them in more concrete models and finally turn them into code. A major remaining weakness in the development chain is the gap between textual or semi-formal requirements and formal models. In...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: IEEE Transactions on Software Engineering
سال: 1994
ISSN: 0098-5589
DOI: 10.1109/32.310666